Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

DataServer modules

The OpenEdge DataServer for ORACLE can run in a variety of configurations. Some configurations involve a single process running on one machine. Others involve multiple processes running on different machines across multiple platforms.

To set up a DataServer configuration, determine which modules you need on which platforms. Then, set up the appropriate executables on those platforms. Table 5–1 lists the possible combinations and describes which executables you must set up on each machine. The term local indicates that a DataServer runs on the same machine as the client. Remote indicates that a DataServer runs on a different machine than the client.

Table 5–1: DataServer Configurations

Client	DataServer	Installing and configuring
Windows	Local Windows	Use the default OpenEdge client executable (prowin32.exe). This executable also allows you to use ORACLE networking to access ORACLE.
Windows	Remote Windows	On the client machine, use the default OpenEdge client executable (prowin32.exe). In the Windows host machine, use either the default broker executable (_probrkr.exe) or configure the broker using Progress Explorer.
Windows	Remote UNIX	On the client machine, use the default OpenEdge client executable (prowin32.exe). On the UNIX host machine, use the default broker executable (_probrkr) and set ORASRV to point to the _orasrv DataServer executable. This executable supports OpenEdge networking.
UNIX	Local UNIX	On the UNIX client machine, use the default client executable (_progres). This executable also allow you to use ORACLE networking to access ORACLE.
UNIX	Remote UNIX	On the UNIX client machine, use the default client executable (_progres). On the UNIX host machine, use the default broker executable (_probrkr) and set ORASRV to point to the _orasrv DataServer executable. These executables support OpenEdge networking.
UNIX	Remote Windows	On the UNIX client machine, use the default client executable (_progres). In the Windows host machine, use either the default broker executable (_probrkr.exe) or configure using Progress Explorer.

Note: If you are using a DataServer on a UNIX platform where ORACLE does not support shared objects, you must build your DataServer executables instead of using the default client and DataServer executables. See Appendix D, "Building DataServer Executables," for instructions.

For instructions on setting up your DataServer configuration, see the section or sections that apply to the platform you are considering. For example, if you are configuring a local DataServer where all the OpenEdge modules run on the same UNIX machine, see the "Configuring UNIX modules" section. If you are building a remote DataServer configuration with a UNIX client accessing a Windows host, see the "Configuring UNIX modules" section for instructions on setting up the client and the "Configuring Windows modules" section for instructions on setting up the host.